Update privileges for pcr in v25.2 #19605

Name	Link
🔨 Latest commit	`59b0719`
🔍 Latest deploy log	https://app.netlify.com/projects/cockroachdb-interactivetutorials-docs/deploys/683884782aa8be000809a82b

netlify · 2025-05-13T12:36:39Z

✅ Netlify Preview

Name	Link
🔨 Latest commit	`59b0719`
🔍 Latest deploy log	https://app.netlify.com/projects/cockroachdb-docs/deploys/683884788aa92300085574a8
😎 Deploy Preview	https://deploy-preview-19605--cockroachdb-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

katmayb · 2025-05-13T20:13:46Z

src/current/v25.2/set-up-physical-cluster-replication.md

@@ -200,17 +200,6 @@ Connect to your standby cluster's system virtual cluster using [`cockroach sql`]
    --certs-dir "certs"
    ~~~

-1. Add your cluster organization and [{{ site.data.products.enterprise }} license]({% link {{ page.version.version }}/licensing-faqs.md %}#types-of-licenses) to the cluster:


Taking this out because of the licensing change. (I should go back through to v24.3 and make sure to remove.)

suggest pls go back and remove from v24.3 and v25.1 if at all possible :-)

alicia-l2

LGTM except I think we should remove all mention of the SET REPLICATION SOURCE EXPIRATION WINDOW = duration. I think this is too much information for the user and can result in unexpected behavior for the source cluster, which we also don't test. See https://cockroachlabs.slack.com/archives/CJXBR3693/p1747684142786379?thread_ts=1746716551.106479&cid=CJXBR3693

src/current/v24.1/create-virtual-cluster.md

src/current/v25.2/alter-virtual-cluster.md

msbutler · 2025-05-27T15:57:10Z

src/current/v25.2/alter-virtual-cluster.md

@@ -58,15 +57,15 @@ You can use the following options with `ALTER VIRTUAL CLUSTER {vc} START REPLICA

 Option | Value | Description
 -------+-------+------------
-`EXPIRATION WINDOW` | Duration | Override the default producer job's expiration window of 24 hours. The producer job expiration window determines how long the producer job will continue to run without a heartbeat from the consumer job. For more details, refer to the [Technical Overview]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}).
+`EXPIRATION WINDOW` | Duration | Override the default producer job's expiration window of 24 hours from the primary cluster. The producer job expiration window determines how long the producer job will continue to run without a heartbeat from the consumer job. For more details, refer to the [Technical Overview]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}).


i think expiration window and retention need to be removed.

katmayb · 2025-05-27T17:11:45Z

src/current/v25.2/alter-virtual-cluster.md

@@ -40,8 +40,6 @@ Parameter | Description
 `PAUSE REPLICATION` | Pause the replication stream.
 `RESUME REPLICATION` | Resume the replication stream.
 `COMPLETE REPLICATION TO` | Set the time to complete the replication. Use: <br><ul><li>`SYSTEM TIME` to specify a [timestamp]({% link {{ page.version.version }}/as-of-system-time.md %}). Refer to [Fail over to a point in time]({% link {{ page.version.version }}/failover-replication.md %}#fail-over-to-a-point-in-time) for an example.</li><li>`LATEST` to specify the most recent replicated timestamp. Refer to [Fail over to a point in time]({% link {{ page.version.version }}/failover-replication.md %}#fail-over-to-the-most-recent-replicated-time) for an example.</li></ul>
-`SET REPLICATION RETENTION = duration` | Change the [duration]({% link {{ page.version.version }}/interval.md %}) of the retention window that will control how far in the past you can [fail over]({% link {{ page.version.version }}/failover-replication.md %}) to.<br><br>{% include {{ page.version.version }}/physical-replication/retention.md %}
-<span class="version-tag">New in v25.2:</span> `SET REPLICATION SOURCE EXPIRATION WINDOW = duration` | Override the default producer job's expiration window of 24 hours from the primary cluster. The producer job expiration window determines how long the producer job will continue to run without a heartbeat from the consumer job. For more details, refer to the [Technical Overview]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}).


OK to remove SET REPLICATION SOURCE EXPIRATION WINDOW too? @msbutler

yeah, i think we want to remove that documentation too https://cockroachlabs.slack.com/archives/CJXBR3693/p1747688082011559?thread_ts=1746716551.106479&cid=CJXBR3693

OK, removed

alicia-l2

Let some comments but otherwise looks good -- thank you!

alicia-l2 · 2025-05-27T18:06:21Z

src/current/v25.2/alter-virtual-cluster.md

@@ -41,8 +40,6 @@ Parameter | Description
 `PAUSE REPLICATION` | Pause the replication stream.
 `RESUME REPLICATION` | Resume the replication stream.
 `COMPLETE REPLICATION TO` | Set the time to complete the replication. Use: <br><ul><li>`SYSTEM TIME` to specify a [timestamp]({% link {{ page.version.version }}/as-of-system-time.md %}). Refer to [Fail over to a point in time]({% link {{ page.version.version }}/failover-replication.md %}#fail-over-to-a-point-in-time) for an example.</li><li>`LATEST` to specify the most recent replicated timestamp. Refer to [Fail over to a point in time]({% link {{ page.version.version }}/failover-replication.md %}#fail-over-to-the-most-recent-replicated-time) for an example.</li></ul>
-`SET REPLICATION RETENTION = duration` | Change the [duration]({% link {{ page.version.version }}/interval.md %}) of the retention window that will control how far in the past you can [fail over]({% link {{ page.version.version }}/failover-replication.md %}) to.<br><br>{% include {{ page.version.version }}/physical-replication/retention.md %}
-`SET REPLICATION EXPIRATION WINDOW = duration` | Override the default producer job's expiration window of 24 hours. The producer job expiration window determines how long the producer job will continue to run without a heartbeat from the consumer job. For more details, refer to the [Technical Overview]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}).
 `START REPLICATION OF virtual_cluster_spec ON physical_cluster` | Reset a virtual cluster to the time when the virtual cluster on the promoted standby diverged from it. To reuse as much of the existing data on the original primary cluster as possible, you can run this statement as part of the [failback]({% link {{ page.version.version }}/failover-replication.md %}#failback) process. This command fails if the virtual cluster was not originally replicated from the original primary cluster. Refer to [Options](#options) for details on how you can configure a PCR stream initiated as a failback.
 `START SERVICE SHARED` | Start a virtual cluster so it is ready to accept SQL connections after failover.
 `RENAME TO virtual_cluster_spec` | Rename a virtual cluster.


I'm having trouble leaving a comment on the actual section which is 'Options' but I don't think I understand what that section means. Does that mean that if you have a reader cluster running you need to include that SQL syntax during the failover?

I thought we didn't need to do that

Do you mean ALTER VIRTUAL CLUSTER .... with READ VIRTUAL CLUSTER? @msbutler I'm pretty sure confirmed with me that we should keep that in — sorry was trying to find the thread.

Yeah, I just don't understand the use case here.

yes, we need to keep this option (with READER VIRTUAL CLUSTER or whatever it is) . It's used in the reader tenant upgrade flow. https://cockroachlabs.slack.com/archives/C06G041QAMC/p1746624798507089

alicia-l2 · 2025-05-27T18:08:17Z

src/current/v25.2/alter-virtual-cluster.md

 `READ VIRTUAL CLUSTER` | N/A | ([**Preview**]({% link {{ page.version.version }}/cockroachdb-feature-availability.md %}#features-in-preview)) Configure the PCR stream to allow reads from the standby cluster. <br>**Note:** This only allows for reads on the standby's virtual cluster. You cannot perform writes or schema changes to user tables while connected to the standby virtual cluster. For more details, refer to [Start the failback process](#start-the-failback-process).
-`RETENTION` | Duration | Change the [duration]({% link {{ page.version.version }}/interval.md %}) of the retention window that will control how far in the past you can [fail over]({% link {{ page.version.version }}/failover-replication.md %}) to.<br><br>{% include {{ page.version.version }}/physical-replication/retention.md %}

 ## Examples

 ### Start the failover process



I think the 'Start the failover process' should be combined with the 'start a virtual cluster,' or rather, the 'start a virtual cluster' part should be a subsection of the failover process section. This is because generally the 'failover' isn't complete until the standby cluster is ready to receive traffic. So I think we should put these two steps together into one 'Failover process' section.

alicia-l2 · 2025-05-27T18:28:15Z

src/current/v25.2/drop-virtual-cluster.md

@@ -24,7 +24,7 @@ The `DROP VIRTUAL CLUSTER` statement will delete all data related to the specifi
 `DROP VIRTUAL CLUSTER` requires one of the following privileges:


Can we add "if a user wanted to completely restart their PCR stream, they would drop their old VC and create a new VC via a replication stream." some additional context on why one would do this?

msbutler · 2025-05-28T12:57:29Z

src/current/v24.1/alter-virtual-cluster.md


-When a virtual cluster is [`ready`]({% link {{ page.version.version }}/show-virtual-cluster.md %}#responses) after initiating the cutover process, you must start the service so that the virtual cluster is ready to accept SQL connections:
+To [cut back]({% link {{ page.version.version }}/cutover-replication.md %}#cutback) to a cluster that was previously the primary cluster, use the `ALTER VIRTUAL CLUSTER` syntax:


So just to clarify, in 24.1 docs, what we normally call failback, we call cutback? Perhaps in a follow up PR we should make this consistent.

Agree the consistency would be best across versions, but I think we "formally" switched over the name at that version and didn't backport the change for syntax reasons. I'll look back over communication here, and add to the list.

msbutler · 2025-05-28T12:58:35Z

src/current/v24.1/create-virtual-cluster.md

@@ -77,9 +67,9 @@ Value | Description
 Cockroach Labs does not recommend changing the default capabilities of created virtual clusters.
 {{site.data.alerts.end}}

-_Capabilities_ control what a virtual cluster can do. When you start a replication stream, you can specify a virtual cluster with `LIKE` to ensure other virtual clusters on the standby cluster will work in the same way. `LIKE` will refer to a virtual cluster on the CockroachDB cluster you're running the statement from.
+_Capabilities_ control what a virtual cluster can do. The configuration profile included at startup creates the `template` virtual cluster with the same set of capabilities per CockroachDB version. When you start a replication stream, you can specify the `template` VC with `LIKE` to ensure other virtual clusters on the standby cluster will work in the same way. `LIKE` will refer to a virtual cluster on the CockroachDB cluster you're running the statement from.


this should be removed entirely right?

I'm going to just tackle capabilities next week. https://cockroachlabs.atlassian.net/browse/DOC-13797

I had to change that in this PR because that link was breaking the build.

msbutler · 2025-05-28T13:56:38Z

src/current/v25.2/alter-virtual-cluster.md


- The `admin` role.
- The `MANAGEVIRTUALCLUSTER` [system privilege]({% link {{ page.version.version }}/security-reference/authorization.md %}#privileges) allows the user to run all the related `VIRTUAL CLUSTER` SQL statements for PCR.
+{% include_cached new-in.html version="v25.2" %} The `ALTER VIRTUAL CLUSTER ... SET REPLICATION SOURCE` statement requires the `REPLICATIONSOURCE` system privilege and the `MANAGEVIRTUALCLUSTER` privilege.


this can be removed, since we're no longer documenting this cmd.

Removed. I've made an issue for myself to clear up any last mentions of these, which can coincide with the updated diagrams as they merge from the cockroach repo https://cockroachlabs.atlassian.net/browse/DOC-13800

msbutler · 2025-05-28T13:58:03Z

src/current/v25.2/alter-virtual-cluster.md

@@ -41,8 +40,6 @@ Parameter | Description
 `PAUSE REPLICATION` | Pause the replication stream.
 `RESUME REPLICATION` | Resume the replication stream.
 `COMPLETE REPLICATION TO` | Set the time to complete the replication. Use: <br><ul><li>`SYSTEM TIME` to specify a [timestamp]({% link {{ page.version.version }}/as-of-system-time.md %}). Refer to [Fail over to a point in time]({% link {{ page.version.version }}/failover-replication.md %}#fail-over-to-a-point-in-time) for an example.</li><li>`LATEST` to specify the most recent replicated timestamp. Refer to [Fail over to a point in time]({% link {{ page.version.version }}/failover-replication.md %}#fail-over-to-the-most-recent-replicated-time) for an example.</li></ul>
-`SET REPLICATION RETENTION = duration` | Change the [duration]({% link {{ page.version.version }}/interval.md %}) of the retention window that will control how far in the past you can [fail over]({% link {{ page.version.version }}/failover-replication.md %}) to.<br><br>{% include {{ page.version.version }}/physical-replication/retention.md %}
-`SET REPLICATION EXPIRATION WINDOW = duration` | Override the default producer job's expiration window of 24 hours. The producer job expiration window determines how long the producer job will continue to run without a heartbeat from the consumer job. For more details, refer to the [Technical Overview]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}).
 `START REPLICATION OF virtual_cluster_spec ON physical_cluster` | Reset a virtual cluster to the time when the virtual cluster on the promoted standby diverged from it. To reuse as much of the existing data on the original primary cluster as possible, you can run this statement as part of the [failback]({% link {{ page.version.version }}/failover-replication.md %}#failback) process. This command fails if the virtual cluster was not originally replicated from the original primary cluster. Refer to [Options](#options) for details on how you can configure a PCR stream initiated as a failback.
 `START SERVICE SHARED` | Start a virtual cluster so it is ready to accept SQL connections after failover.
 `RENAME TO virtual_cluster_spec` | Rename a virtual cluster.


yes, we need to keep this option (with READER VIRTUAL CLUSTER or whatever it is) . It's used in the reader tenant upgrade flow. https://cockroachlabs.slack.com/archives/C06G041QAMC/p1746624798507089

msbutler · 2025-05-28T14:02:45Z

src/current/v24.2/create-virtual-cluster.md

@@ -77,9 +67,9 @@ Value | Description
 Cockroach Labs does not recommend changing the default capabilities of created virtual clusters.
 {{site.data.alerts.end}}

-_Capabilities_ control what a virtual cluster can do. When you start a replication stream, you can specify a virtual cluster with `LIKE` to ensure other virtual clusters on the standby cluster will work in the same way. `LIKE` will refer to a virtual cluster on the CockroachDB cluster you're running the statement from.
+_Capabilities_ control what a virtual cluster can do. The configuration profile included at startup creates the `template` virtual cluster with the same set of capabilities per CockroachDB version. When you start a replication stream, you can specify the `template` VC with `LIKE` to ensure other virtual clusters on the standby cluster will work in the same way. `LIKE` will refer to a virtual cluster on the CockroachDB cluster you're running the statement from.


i think this can be removed?

rmloveland

LGTM but see my comments re: retroactively removing features and there doesn't seem to be a DOC ticket saying to do that so we can find the provenance of this change in the future

rmloveland · 2025-05-29T14:58:14Z

src/current/v23.2/alter-virtual-cluster.md

@@ -66,19 +65,6 @@ You can use either:
 - `SYSTEM TIME` to specify a [timestamp]({% link {{ page.version.version }}/as-of-system-time.md %}).
 - `LATEST` to specify the most recent replicated timestamp.

-### Set a retention window


i don't see from either of the linked issues that they talk about removing these retention & expiration options, but i am probably not reading them right. if i am reading them right and maybe this is an opportunistic edit, is there a JIRA tracking this part of the work we can refer to in future?

Yes, apologies Rich, issue now linked. This was a last-minute decision that should have gone into a separate PR. There will also be follow-up work on this.

rmloveland · 2025-05-29T14:59:19Z

src/current/v23.2/create-virtual-cluster.md

@@ -38,16 +38,8 @@ GRANT SYSTEM MANAGEVIRTUALCLUSTER TO user;
 Parameter | Description
 ----------+------------
 `virtual_cluster_name` | The name for the new virtual cluster.
-`LIKE virtual_cluster_spec` | Creates a virtual cluster with the same [capabilities](#capabilities) and settings as another virtual cluster.


it seems weird that we are ripping features out of a very old release like this? maybe this is all happening via team discussions so apologies if so. just seems quite unusual to be removing stuff this far back

PS on further review, suggest checking if this has interactions with any 'known limitations' or 'backward-incompatible changes' we published in these earlier release docs

rmloveland · 2025-05-29T15:02:12Z

src/current/v23.2/drop-virtual-cluster.md

@@ -47,13 +47,20 @@ Parameter | Description

 ## Examples

-### Remove a virtual cluster
+### Restart a PCR stream


opportunistic edit?

rmloveland · 2025-05-29T15:09:05Z

src/current/v24.2/drop-virtual-cluster.md

-
-
-The `DROP VIRTUAL CLUSTER` statement removes virtual clusters. Virtual clusters are used only as part of the [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow.
+The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a **physical cluster replication (PCR)** stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow.


officially (*) we don't need to update v24.2 docs anymore

(*) except unofficially we do because google can still find stuff in them :-/

Yes, though, I forgot, but maybe it's good to update them for these cases (particularly removal of options)

rmloveland · 2025-05-29T15:11:29Z

src/current/v25.2/create-virtual-cluster.md

@@ -19,12 +19,12 @@ Physical cluster replication is only supported in CockroachDB {{ site.data.produ

 ## Required privileges

-`CREATE VIRTUAL CLUSTER` requires one of the following privileges:
+{% include_cached new-in.html version="v25.2" %} The following [privileges]({% link {{ page.version.version }}/security-reference/authorization.md %}) are required to start a PCR stream with `CREATE VIRTUAL CLUSTER`:


suggest adding #supported-privileges to the link to save users a scroll

rmloveland · 2025-05-29T15:12:49Z

src/current/v25.2/set-up-physical-cluster-replication.md

@@ -105,7 +105,7 @@ Connect to your primary cluster's system virtual cluster using [`cockroach sql`]

 ### Create a replication user and password

-The standby cluster connects to the primary cluster's system virtual cluster using an identity with the `REPLICATION` privilege. Connect to the primary cluster's system virtual cluster and create a user with a password:
+The standby cluster connects to the primary cluster's system virtual cluster using an identity with the `REPLICATIONSOURCE` privilege. Connect to the primary cluster's system virtual cluster and create a user with a password:


suggest linking this use of "privilege" with the privileges docs

rmloveland · 2025-05-29T15:13:53Z

src/current/v25.2/set-up-physical-cluster-replication.md

@@ -200,17 +200,6 @@ Connect to your standby cluster's system virtual cluster using [`cockroach sql`]
    --certs-dir "certs"
    ~~~

-1. Add your cluster organization and [{{ site.data.products.enterprise }} license]({% link {{ page.version.version }}/licensing-faqs.md %}#types-of-licenses) to the cluster:


suggest pls go back and remove from v24.3 and v25.1 if at all possible :-)

katmayb force-pushed the privileges-pcr-25.2 branch from e70c0e4 to 6189e9e Compare May 13, 2025 15:17

katmayb commented May 13, 2025

View reviewed changes

katmayb force-pushed the privileges-pcr-25.2 branch from 6189e9e to e6125ac Compare May 19, 2025 18:50

katmayb requested review from msbutler and alicia-l2 May 19, 2025 18:52

katmayb marked this pull request as ready for review May 19, 2025 18:52

alicia-l2 approved these changes May 19, 2025

View reviewed changes

katmayb force-pushed the privileges-pcr-25.2 branch from e6125ac to 4582dee Compare May 21, 2025 16:10

msbutler reviewed May 27, 2025

View reviewed changes

src/current/v24.1/create-virtual-cluster.md Outdated Show resolved Hide resolved

msbutler reviewed May 27, 2025

View reviewed changes

src/current/v25.2/alter-virtual-cluster.md Outdated Show resolved Hide resolved

msbutler reviewed May 27, 2025

View reviewed changes

katmayb commented May 27, 2025

View reviewed changes

alicia-l2 approved these changes May 27, 2025

View reviewed changes

msbutler reviewed May 28, 2025

View reviewed changes

msbutler approved these changes May 28, 2025

View reviewed changes

katmayb requested a review from rmloveland May 28, 2025 16:49

rmloveland approved these changes May 29, 2025

View reviewed changes

katmayb added 6 commits May 29, 2025 11:59

Update privileges for pcr in v25.2

865ce71

Adjust for only privileges + expir/retention removal

c12c0c4

Missed retention expiration options

9875d9e

Feedback

f33153e

Feedback adjustments

a88504b

Docs feedback

59b0719

katmayb force-pushed the privileges-pcr-25.2 branch from 2aa99e0 to 59b0719 Compare May 29, 2025 15:59

katmayb merged commit b3071fe into main May 29, 2025
6 checks passed

katmayb deleted the privileges-pcr-25.2 branch May 29, 2025 16:10

		@@ -24,7 +24,7 @@ The `DROP VIRTUAL CLUSTER` statement will delete all data related to the specifi
		`DROP VIRTUAL CLUSTER` requires one of the following privileges:


		When a virtual cluster is [`ready`]({% link {{ page.version.version }}/show-virtual-cluster.md %}#responses) after initiating the cutover process, you must start the service so that the virtual cluster is ready to accept SQL connections:
		To [cut back]({% link {{ page.version.version }}/cutover-replication.md %}#cutback) to a cluster that was previously the primary cluster, use the `ALTER VIRTUAL CLUSTER` syntax:



		The `DROP VIRTUAL CLUSTER` statement removes virtual clusters. Virtual clusters are used only as part of the [physical cluster replication (PCR)]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow.
		The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a physical cluster replication (PCR) stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow.

Update privileges for pcr in v25.2 #19605

Update privileges for pcr in v25.2 #19605

Uh oh!

Conversation

katmayb commented May 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented May 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Files changed:

Uh oh!

netlify bot commented May 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for cockroachdb-api-docs canceled.

Uh oh!

netlify bot commented May 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Uh oh!

netlify bot commented May 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Netlify Preview

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

alicia-l2 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

alicia-l2 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

msbutler May 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

msbutler May 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rmloveland left a comment

katmayb commented May 13, 2025 •

edited

Loading

github-actions bot commented May 13, 2025 •

edited

Loading

netlify bot commented May 13, 2025 •

edited

Loading

netlify bot commented May 13, 2025 •

edited

Loading

netlify bot commented May 13, 2025 •

edited

Loading

msbutler May 28, 2025 •

edited

Loading

msbutler May 28, 2025 •

edited

Loading